You can configure the router to map received packets based on their protocol type.
This option deletes specific address mapping for Ethernet.
Enter the following information:
This parameter specifies the Ethernet protocol type (in hexadecimal).
Valid Values: X'5DD' to X'FFFF'
Protocol - Ethernet type (hex value)
Default Value: 1
This parameter specifies the 6-byte (12-digit hexadecimal) group/multicast address.
Valid Values: X'0000 0000 0000' to X'FFFF FFFF FFFF'
Default Value: none
Select the Submit button.
You can configure the router to map received packets based on their protocol type.
This option deletes specific address mapping for Subnetwork Access Protocol (SNAP).
Enter the following information:
This parameter specifies the SNAP protocol type (in hexadecimal).
In LANs, a 5-byte protocol discriminator that identifies the non-IEEE standard protocol family to which a packet belongs. The SNAP value is used to differentiate between protocols that use X'AA' as their service access point (SAP) value.
The first 6 digits are the Organizationally Unique Identifier (OUI) and the last 2 digits are the Ethernet type value.
Valid Values: X'00 0000 0000' to X'FF FFFF FFFF'
Common values are:
Default Value: 00 0000 0800
This parameter specifies the 6-byte (12-digit hexadecimal) group/multicast address.
Valid Values: X'0000 0000 0000' to X'FFFF FFFF FFFF'
Default Value: none
Select the Submit button.
Removes a port from a bridging configuration. Because Enable Bridge by default configures all LAN devices to participate in bridging, this option allows you to customize which devices should or should not participate in the bridging. The port number value normally is one greater than the interface number.
This option followed by the IP tunnel port number removes an IP tunnel from a bridging configuration.
You can display bridge ports and their corresponding interfaces using List Port.
Enter the port number to be deleted.
Select the Submit button.
You can configure the bridge so that it can selectively filter destination service access point (DSAP) packets based on their protocol type. Filters can be applied to all ports or only to selected ports.
You can display the protocol filter for a specific port using the List Prot-Filter option.
This option deletes previously specified DSAP protocol identifiers used in filtering. You can delete filters for all ports or selected ports.
This parameter specifies the Destination Service Access Point (DSAP) protocol type (in hexadecimal).
Valid Values: X'1' to X'FE'
Common values are:
Protocol - SAP (hexadecimal value)
Default Value: 1
Select the Submit button.
You can configure the bridge so that it can selectively filter Ethernet packets based on their protocol type. Filters can be applied to all ports or only selected ports.
You can display the protocol filter for a specific port using the List Prot-Filter option.
This option deletes previously specified Ethernet protocol identifiers used in filtering. You can delete filters for all ports or selected ports.
Valid Values: X'5DD' to X'FFFF'
Protocol - Ethernet type (hex value)
Default Value: none
Select the Submit button.
You can configure the bridge so that it can selectively filter SNAP packets based on their protocol type. Filters can be applied to all ports or only selected ports.
You can display the protocol filter for a specific port using the List Prot-Filter option.
This option deletes previously specified SNAP protocol identifiers used in filtering. You can delete filters for all ports or selected ports.
This parameter specifies Subnetwork Access Protocol (SNAP) type in a 10-digit hexadecimal format. The first 6 digits are the Organizationally Unique Identifier (OUI) and the last 2 digits are the Ethernet type value.
Valid Values: X'00 0000 0000' to X'FF FFFF FFFF'
Common values are:
Default Value: 00 0000 0800
Select the Submit button.
This option disables the Bridge.
You can use List to display the current configuration.
Select the Submit button.
This option disables the creation of duplicate frames present in mixed bridging environments. When the SR-TB bridging feature is enabled on an 802.5 interface (with source routing and transparent bridging enabled), there are inconsistencies created when bridging frames to an unknown (or multicast) destination. It is not known to the bridge whether the destination is behind a source routing (only) or transparent bridge.
To remedy this situation, the bridge sends out duplicates of these frames (by default). One frame has source routing fields present (a spanning tree explorer RIF) and the other is formatted for transparent bridging (no RIF is present). Normally, you would want both types of frames sent out when in a mixed bridging environment.
However, if you do not want both frame types, Disable duplicate STE lets you eliminate this duplication by disabling the creation of STE frames. In this case, the bridge sends only Transparent Spanning Frames (TSFs) for the transparent bridging environment.
Enter the port number that should not generate STE frames.
Select the Submit button.
To remedy this situation, the bridge sends out duplicates of these frames (by default). One frame has source routing fields present (a spanning tree explorer RIF) and the other is formatted for transparent bridging (no RIF is present). Normally, you would want both types of frames sent out when in a mixed bridging environment.
However, if you do not want both frame types, Disable duplicate TSF lets you eliminate this duplication by allowing you to disable the creation of TSFs. In this case, the bridge sends only STE frames for the source route bridging environment.
Enter the port number that should not generate TSF frames.
Select the Submit button.
This option disables translation of SNA frames to Ethernet Type 2 format as used by IBM RTs running OS/2 EE.
Enter the port number to which this disable option applies.
Select the Submit button.
This option disables a port from allowing propagation of spanning tree explorer frames if source routing is enabled. This option is used only if transparent bridging is not enabled on the port.
Enter the port number.
Select the Submit button.
This option disables source routing on a given port. This option is used to have an already-participating bridge interface discontinue source routing.
Enter the port number.
Select the Submit button.
This option disables the conversion of a source-routed frame to a transparent frame and vice-versa.
This conversion allows for compatibility between Source Routing and Transparent Bridging domains. When this feature is disabled, the bridge will not allow source-routed frames be accepted into a transparent domain.
Default Value: disable
Select the Submit button.
This option disables transparent bridging function on the given port. This option is useful for cases where an alternative communication method such as source routing is desirable and it is used to configure SRB and SR-TB bridge function.
Note: Using this option might bring about an non-valid configuration if not used properly. For instance, using it on an Ethernet interface will result in disabling bridging function for that interface.
Enter the port number.
Select the Submit button.
Disables spanning tree protocol (STP) participation for the bridge on a per-port basis.
Enter the port number.
Select the Submit button.
This option enables the creation of duplicate frames present in mixed bridging environments. When the SR-TB bridging feature is enabled on an 802.5 interface (with source routing and transparent bridging enabled), there are inconsistencies created when bridging frames to an unknown (or multicast) destination. It is not known to the bridge whether the destination is behind a source routing (only) or transparent bridge.
To remedy this situation, the bridge sends out duplicates of these frames (by default). One frame has source routing fields present (a spanning tree explorer RIF) and the other is formatted for transparent bridging (no RIF is present). Normally, you would want both types of frames sent out when in a mixed bridging environment.
Duplicate frame generation is enabled by default.
Enter the port number that should generate STE frames.
Select the Submit button.
This option enables the creation of duplicate frames present in mixed bridging environments. When the SR-TB bridging feature is enabled on an 802.5 interface (with source routing and transparent bridging enabled), there are inconsistencies created when bridging frames to an unknown (or multicast) destination. It is not known to the bridge whether the destination is behind a source routing (only) or transparent bridge.
To remedy this situation, the bridge sends out duplicates of these frames (by default). One frame has source routing fields present (a spanning tree explorer RIF) and the other is formatted for transparent bridging (no RIF is present). Normally, you would want both types of frames sent out when in a mixed bridging environment.
Duplicate frame generation is enabled by default.
Enter the port number that should generate TSF frames.
Select the Submit button.
This option enables the generation of duplicate spanning tree explorer (STE) and transparent spanning frames (TSFs). Duplicate frame generation is enabled by default.
This option enables the creation of duplicate frames present in mixed bridging environments. When the SR-TB bridging feature is enabled on an 802.5 interface (with source routing and transparent bridging enabled), there are inconsistencies created when bridging frames to an unknown (or multicast) destination. It is not known to the bridge whether the destination is behind a source routing (only) or transparent bridge.
To remedy this situation, the bridge sends out duplicates of these frames (by default). One frame has source routing fields present (a spanning tree explorer RIF) and the other is formatted for transparent bridging (no RIF is present). Normally, you would want both types of frames sent out when in a mixed bridging environment.
Duplicate frame generation is enabled by default.
Enter the port number that should generate STE and TSF frames.
Select the Submit button.
This option enables translation of SNA frames to Ethernet Type 2 as used by IBM PC RTs running OS/2 EE. Using this option will result in SNA frames being duplicated into both 802.3/802.2 and IBM-RT formats to unknown hosts on an Ethernet.
Enter the port number that should have this translation enabled.
Select the Submit button.
This option enables the port to allow propagation of spanning tree explorer frames if source routing is enabled. This is valid on token-ring ports only. This feature is enabled by default when source routing is configured on the port.
Enter the port number that should propagate STE frames.
Select the Submit button.
This option enables source routing for a given port. This option is typically used when source routing on part of the bridge is desired. If source routing is the only feature desired, transparent bridging on the interface should be disabled.
The bridge number must be entered only in the first Enable Source-Routing command. If you enter the bridge number on subsequent Enable Source-Routing commands, it will be ignored.
Enter the following information:
Source routing to transparent bridging conversion must be enabled.
Valid Values: X'0' to X'FFF'
Default Value: 1
Select the Submit button.
This value is required when source routing is enabled on the first interface. For later interfaces, this input is optional. The bridge number is used to construct and inspect the Source-Route RI field.
Valid Values: X'0' to X'F'
Default Value: 1
Select the Submit button.
This parameter enables the conversion of a source-routed frame to a transparent frame and vice-versa.
This conversion allows for compatibility between Source Routing and Transparent Bridging domains. When this feature is enabled, the bridge lets source-routed frames be accepted into a transparent domain by stripping off the router information field (RIF) and converting them into transparent frames.
The bridge also gathers routing information concerning source routing stations from the passing source-routing frames. This is obtained from the RIF. This RIF information is then used to convert a transparent frame to a source-routed frame. If a RIF is not available for a station, then the frame is sent out as a spanning tree explorer frame in the source routing domain.
In order for the conversion function to operate properly, the transparent bridging domain must be given a segment number. All SR-TB bridges that are connected to this domain should also be configured with the same segment number.
This parameter specifies the number, in 4-digit hexadecimal, that represents the LAN to which the media is attached. All the media on other bridges attached to this LAN must be configured with the same value for source routing to operate correctly.
Valid Values: X'1' - X'FFF'
Default Value: 1
The maximum transmission unit (MTU) is the number of octets per frame of data that can be transferred across a given physical network. When an IP datagram travels from one host to another, it can cross different physical networks. Some physical networks may have this set MTU which will not allow long IP datagrams to be placed in on physical frame. Fragmentation will occur when you attempt to transmit frames larger than that which the physical network can handle.
Valid Values: 576 to 18000 bytes
Default Value: 2048
Select the Submit button.